Repository navigation
fix(ci): post datadog-api-spec statuses to ddoghq org - #909
Merged
Merged
Conversation
datadog-api-spec moved from DataDog to ddoghq and the DataDog copy is archived, so posting review/CI statuses to DataDog/datadog-api-spec 404s. Point both the octo-sts token scope and the status actions at ddoghq.
MintsInc
marked this pull request as ready for review
October 12, 2026 12:51
damfleu
approved these changes
Oct 12, 2026
![datadog-official[bot]](https://avatars.githubusercontent.com/in/1358509?s=60&v=4){kind=small}
There was a problem hiding this comment.
More details
Both workflows consistently target ddoghq/datadog-api-spec for token issuance and status posting. The completed static review identified no actionable regression.
🤖 Bits Code Review · Commit 7c2e791
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The
datadog-api-specrepository moved from theDataDogorg toddoghq. The status-reporting jobs still targetDataDog/datadog-api-spec, soSend PR Approval Statusnow fails with a 404 on generated PRs, e.g. https://github.com/DataDog/pup/actions/runs/38248983717/job/114810041363?pr=908. Thereportjob inci.ymlhas the same problem.Changes
ddoghq/datadog-api-specand passowner: ddoghqto the status actions, matching the other API client repos.Tests
Not verified yet. These jobs only run on
datadog-api-spec/generated/*branches, so this PR doesn't exercise them. Planned: after merge, push to (or close/reopen) #908 and confirmSend PR Approval Statuspasses and both status checks are posted. Re-running the failed job won't pick up the fix because it reuses the original merge SHA.Appendix
Follow-up:
.github/chainguard/datadog-api-spec.ci-cd.generate.sts.yamlonly trusts the oldDataDog/datadog-api-specand can be removed.